Methods and systems for imaging device credential submission and consolidation

ABSTRACT

Embodiments of the present invention comprise systems, methods and devices for eliminating multiple submission of user credential data in a system with multiple distinct restricted sub-systems wherein a unique credential is required for each sub-system.

RELATED REFERENCES

This application is a continuation-in-part of U.S. patent application Ser. No. 10/962,248, entitled “Methods and Systems for Imaging Device Remote Application Interaction, filed on Oct. 8, 2004; this application is also a continuation-in-part of U.S. patent application Ser. No. 10/961,793, entitled “Methods and Systems for Imaging Device Remote Form Management, filed on Oct. 8, 2004; this application is also a continuation-in-part of U.S. patent application Ser. No. 10/961,911, entitled “Methods and Systems for Imaging Device Remote Location Functions, filed on Oct. 8, 2004; this application is also a continuation-in-part of U.S. patent application Ser. No. 10/961,594, entitled “Methods and Systems for Imaging Device Remote document Management, filed on Oct. 8, 2004; and this application is also a continuation-in-part of U.S. patent application Ser. No. 10/962,103, entitled “Methods and Systems for Imaging Device Document Translation, filed on Oct. 8, 2004; this application also claims the benefit of U.S. Provisional Patent Application No. 60/704,066, entitled “Methods and Systems for Imaging Device Applications,” filed Jul. 28, 2005.

FIELD OF THE INVENTION

Embodiments of the present invention comprise methods and systems for eliminating multiple submission of user credential data in a system with multiple distinct restricted sub-systems wherein a unique credential is required for each sub-system.

BACKGROUND

Imaging devices such as printers, copiers, scanners and fax machines can have a wide array of functions and capabilities to fit specific uses or combinations of uses. Imaging devices often take the form of a multi-function peripheral device (MFP) that combines the functions of two or more of the traditionally separated imaging devices. An MFP may combine any number of imaging devices, but typically comprises the functions of a printer, scanner, copier and fax machine.

Some imaging devices may contain computing resources for data storage and processing such as processors, hard disk drives, memory and other devices. As imaging devices add more features and functions, they become more costly and complex.

More complex imaging devices and MFPs may comprise network connectivity to provide communication with other computing devices, such as personal computers, other imaging devices, network servers and other apparatus. This connectivity allows the imaging device to utilize off-board resources that are available on a connected network.

Imaging devices typically have a user input panel with an array of buttons, knobs and other user input devices. Some devices also have a display panel, which can be for display only or can be a touch panel display that enables user input directly on the display.

Devices with touch panel displays or displays with buttons arranged in cooperation with the display can display menu data that may be selected by user input. This menu data is typically driven by an on-board server module within the imaging device.

BRIEF SUMMARY OF THE INVENTION

Some embodiments of the present invention comprise methods and systems for management of credential data that is used to gain access to restricted systems and services.

Some embodiments of the present invention comprise methods and systems for eliminating multiple submission of user credential data in a system with multiple distinct restricted sub-systems wherein a unique credential is required for each sub-system.

The foregoing and other objectives, features, and advantages of the invention will be more readily understood upon consideration of the following detailed description of the invention taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL DRAWINGS

FIG. 1 is a diagram of an embodiment of the present invention comprising an imaging device in connection with a remote computing device;

FIG. 2 is an image of an exemplary user interface for an imaging device;

FIG. 3 shows an exemplary imaging device;

FIG. 4 is a chart depicting steps of an imaging device method;

FIG. 5 is a chart depicting steps of an imaging device method using a markup language;

FIG. 6 shows an exemplary remote computing device embodiment;

FIG. 7 is a diagram showing components of an exemplary remote computing device;

FIG. 8 is a chart showing steps of a remote computing device method;

FIG. 9 is a chart showing steps of a remote computing device method using a markup language;

FIG. 10 is a diagram showing a system comprising multiple imaging devices in connection with a remote computing device;

FIG. 11 is a chart showing steps of a method comprising RCD processing of user input data;

FIG. 12 is a diagram showing components of some embodiments comprising linked resources;

FIG. 13A is a diagram of some system embodiments of the present invention comprising an imaging device, a single sign-on server application (SOSSA) and a service;

FIG. 13B is a diagram of some system embodiments of the present invention comprising an imaging device, an access-control application, a single sign-on server application (SOSSA) and a service;

FIG. 14 is a diagram of an exemplary user credential data table;

FIG. 15 is a chart depicting steps of a method of some embodiments comprising a single sign-on server application in direct communication with an IDev;

FIG. 16 is a chart showing the steps of a method of some embodiments comprising IDev, SSOSA and service interaction;

FIG. 17 is a chart showing the steps of a method of some embodiments comprising SSO token request and issuance through an AccApp;

FIG. 18 is a chart showing the steps of a method of some embodiments comprising an IDev in direct communication with an SSOSA;

FIG. 19 is a chart showing the steps of a method of some embodiments comprising an IDev communication with an SSOSA through an AccApp;

FIG. 20 is a chart showing the steps of a method of some embodiments comprising sending an SSO token to a service and receiving access;

FIG. 21 is a chart showing the steps of a method of some embodiments comprising an SSOSA receiving an SSO token request directly from an IDev;

FIG. 22 is a chart showing the steps of a method of some embodiments comprising an SSOSA receiving an SSO token request from an AccApp;

FIG. 23 is a chart showing the steps of a method of some embodiments comprising sending user service credential data from an SSOSA to a service;

FIG. 24 is a chart showing the steps of a method of some embodiments comprising authenticating sign on credentials and requesting an SSO token from an AccApp; and

FIG. 25 is a chart showing the steps of a method of some embodiments comprising a service exchanging an SSO token for user service credentials.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Embodiments of the present invention will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. The figures listed above are expressly incorporated as part of this detailed description.

It will be readily understood that the components of the present invention, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the embodiments of the methods and systems of the present invention is not intended to limit the scope of the invention but it is merely representative of the presently preferred embodiments of the invention.

Elements of embodiments of the present invention may be embodied in hardware, firmware and/or software. While exemplary embodiments revealed herein may only describe one of these forms, it is to be understood that one skilled in the art would be able to effectuate these elements in any of these forms while resting within the scope of the present invention.

Embodiments of the present invention comprise interfaces and architecture that integrate imaging devices with remote computing device applications and environments to provide solutions that may not be possible solely with an imaging device alone. Some embodiments comprise an infrastructure and set of interfaces that allow applications on a network to programmatically control imaging device functions and interact with a user through an imaging device input panel. Software functions that are not practical within the imaging device can be performed on the server but are accessible from the imaging device.

For the purposes of this specification and claims, an imaging device (IDev) may be described as a device that performs an imaging function. Imaging functions comprise scanning, printing, copying, image transmission (sending and receiving), image conversion and other functions. Exemplary imaging devices comprise printers, copiers, facsimile machines, scanners, computing devices that transmit, convert or process images and other devices. An IDev may also perform multiple imaging functions. For example, and not by way of limitation, a multi-function peripheral device (MFP), which typically has the capability to perform a plurality of functions comprising a printer, scanner, copier and/or a facsimile machine or image transmitter/receiver, is a type of imaging device. Other MFP imaging devices may comprise other combinations of functions and still qualify as an IDev.

For the purposes of this specification and claims, a remote computing device (RCD) is a device capable of processing data and communicating with other devices through a communications link. An RCD is a remote device because it requires a communications link, such as a network connection, a telephone line, a serial cable or some other wired or wireless link to communicate with other devices such as an imaging device. Some exemplary RCDs are network servers, networked computers and other processing and storage devices that have communications links.

Some embodiments of the present invention may be described with reference to FIGS. 1 & 2. These embodiments comprise an imaging device (IDev) 4 that may be a multi-function peripheral device (MFP) or a single function device. The imaging device 4 further comprises a user interface (UI) panel 2, which may comprise input buttons 14 and a display device 12 or may comprise a touch panel system with or without buttons 14. User input and display may also be performed through a separate UI device 8, which may be connected to the imaging device 4 by a communication link 12, such as a USB connection, a network cable, a wireless connection or some other communications link. UI device 8 may comprise an input device, such as a keyboard or buttons as well as a display device, which may also be a touch screen panel. UI device 8 may also comprise an interface for transfer of instructions that are input to the device 8 from a remote input device. This form of UI device 8 may comprise memory sticks, USB memory cards and other storage devices that may be configured to store input for transfer to an imaging device.

These embodiments further comprise a remote computing device (RCD) 6 that is linked to the imaging device 4 via a communications link 10, such as a network connection. This network connection may be a typical wired connection or a wireless link.

Embodiments of the present invention may provide menu data from the RCD 6 to the imaging device UI panel 2 or remote panel 8 via the network connection 10. Once this menu data is fed to the imaging device 4, an UI panel 2, 8 on the imaging device 4 may be used to interact with applications that run on the remote computing device 6. User input received from UI panels 2, 8 may be returned directly to the remote computing device 6.

A Web Service is a software application identified by a Uniform Resource Identifier (URI), whose interfaces and binding are capable of being defined, described and discovered by Extensible Markup Language (XML) artifacts and supports direct interactions with other software applications using XML based messages via Internet-based protocols.

An application on the remote computing device 6 may use one or more Web Services to control various features in the imaging device 4, such as enabling, disabling or setting device values or controlling device functions.

Embodiments of the present invention allow network applications running on remote computing devices to interact with the user of the imaging device through the imaging device I/O panel. These embodiments allow imaging device user interface (UI) control (i.e., touch panel, button/display) by applications. Some embodiments may also integrate custom display screens or menus with the native imaging device UI. Embodiments may hand off control of imaging device functions between standard operation modes performed on the imaging device in response to user input to an imaging device UI and open systems modes that utilize network resources, such as applications on RCDs, through user input at the imaging device UI.

Embodiments of the present invention comprise network-based applications that have full control over the imaging device UI to display text and graphics in any format. In these embodiments, the application can programmatically display buttons, textboxes, graphics, etc. in any layout desired.

In some embodiments, the UI layout is easy to program using a standard language, such as a markup language. These languages comprise Hypertext Markup Language (HTML), Extensible Markup Language (XML), Wireless Markup Language (WML), Extensible Hypertext Markup Language (XHTML) and other languages.

In some embodiments of the present invention a remote computing device application or server application is able to request a keyboard UI to be displayed on the imaging device display 12, 8. In some embodiments, this functionality is available on the imaging device and does not need to be recreated by remote computing device applications. In some embodiments, the remote computing device may define the keyboard prompt and default values. These embodiments may comprise a remote computing device that is able to rename imaging device UI buttons, such as the OK and Cancel buttons as well as define additional buttons.

In some embodiments, menu templates may be served to the imaging device UI by the imaging device itself 4 or from a remote computing device 6.

External Authorization Application

Some embodiments of the present invention may comprise a remote computing device application that is registered as the External Authorization server. The External Authorization application may control access to the imaging device and may have top-level control of the UI. UI control may be given to this application in the same manner that control is given to an internal auditor.

In these embodiments, when an imaging device system boots, it checks to see if an External Authorization application is registered. If so, the imaging device is placed in disabled mode and the application is contacted to take control of the UI. If the External Authorization server is not available, an error message may be displayed and the device may remain disabled. The imaging device may periodically try to contact the External Authorization server until it is available. Table 1 below describes what entity has control of the UI, in an exemplary embodiment, when the device is in a disabled state.

TABLE 1 UI Control in Disabled State Indicator Button Press UI Control Lights Device boots External Application None Document Filing External Application None Image Send External Application None Copy External Application None Job Status Device - standard Job Status screens Job Status Custom Settings Device - standard Custom Settings N/A screens OS Mode Not available when device is disabled Remote Computing Device Applications

In embodiments of the present invention, access to the custom UI panels of imaging devices may vary from application to application. Some solutions, such as Document Management integration, may wish to leverage the native Image Send screens, but display some custom UI's to gather additional information about a scan job. Other solutions, like custom printing applications, may be accessed from a separate mode than the native functions.

In order to accommodate the diversified needs of these solutions applications, embodiments may support multiple integration points for UI control. These integration points are based on a user action (“trigger”) for which applications may register. In some embodiments, applications may be registered with target devices so that the device knows that when “tigger A” occurs on the front panel to contact “remote computing device B” for instructions. In exemplary embodiments, applications may be integrated with an imaging device at any of several “trigger” points.

Remote computing devices may be registered to a specific function and contacted when that function's hardware key is pressed (e.g. Image Send) on the imaging device UI. Any UI information provided by the remote computing device may be displayed instead of the standard function screens native to the imaging device. This trigger may be used for applications that wish to replace the existing functions with completely custom UI's, such as an alternative scan solution or a specialized display, such as a “Section 508” compatible screen or other specialized-need interface that may have large buttons or other accommodations.

In some embodiments, each function on the imaging device may have a menu on the touch screen that remote computing devices, such as servers, can register. This enables solutions applications to provide custom content and still use some of the standard functionality provided by the imaging device. When a button assigned to a custom application is selected, a menu will be displayed with the solutions registered to that function. Users may select the desired solution and the remote computing device will be contacted for instructions.

In some embodiments, a stand-alone RCD mode that provides remote computing device application access can be accessed from the job queue portion of the UI that is displayed on every screen. This trigger point may be used for applications that do not fit within one of the standard device functions, such as custom printing solutions on an imaging device. When the RCD menu is selected, a menu will be displayed with the solutions applications registered to the generic RCD mode. Users will select the desired solution and the remote computing device will be contacted for instructions.

Hardware Key Interaction

In some embodiments of the present invention, when an imaging device is enabled, additional hardware keys may be used to manage the device. Hardware key assignments for an exemplary embodiment are shown in table 2.

TABLE 2 Exemplary Hardware Key Assignments Button Press Standard IDev Mode RCD Mode Mode keys (Copy, Clear current job Clear current job Doc Filing, Image settings, move to settings, move to Send) and Custom target screen target screen Settings key Job Status key Move to Job Status, Move to Job Status, maintain current maintain current settings & UI settings & UI location location Clear (C) Clears settings Sends clear event to external application Clear All (CA) Clears settings, Cancels job and cancels job, and returns to default returns to default IDev screen IDev screen (notification sent to external application) **When External Authorization is controlling the UI, only notification is sent Start Initiates scan Initiates scan function function Number keys Input for copy Not used count or fax numbers * Logs user out Logs user out (disable device (disable device and contact External and contact External Authorization for Authorization for screens) screens)

In some embodiments, in addition to the * key for logout, a timeout period may be implemented. Some embodiments also comprise an auto clear setting that can be configured for a given period of time, such as 10 to 240 seconds (or disabled). In these embodiments, when there is no activity for the time configured in auto clear, the device may automatically return to disabled mode and attempt to contact a remote computing device to retake control of the UI.

Error & Jam Notifications

Depending on a particular solution, a remote computing device application may have full or only partial control of the imaging device UI and a particular imaging job. In some embodiments, partial control may include cases where a remote computing device is monitoring clicks, but native modes are responsible for the UI interaction and controlling the job. Partial control may also include cases where the remote computing device application is integrated with a native mode (UI trigger=function custom menu). In these embodiments, the imaging device may handle all error and jam notifications with only a notification sent to the relevant remote computing device application.

For some embodiments, in cases where the remote computing device application has full control over the UI and the job, error and jam notifications may be handled differently depending on the type of error. For recoverable errors, a notification may be sent to the remote computing device application and the application may be responsible for displaying messages and resolving the error. For non-recoverable errors, the imaging device and RCD mode may interact to gracefully handle the error condition (e.g. provide user with instructions for clearing jam).

Control Handoffs

In some embodiments, at different points throughout an imaging job, several applications may need control over an imaging device including, but not limited to, an External Authorization application, a standard RCD application, an imaging device native mode and other applications. The following section describes, for an exemplary embodiment, the various steps in an exemplary job, the entities that may have control during each step, and what type of control may be allowed.

Step 1: User provides credentials to access the device at the device UI. This step may be controlled by a remote computing device, such as an External Authorization application or by Internal Accounting (native mode) in the imaging device itself. At the end of this step, the device is enabled. The External Authorization application may also specify default parameters or disable specific job parameters (e.g. default file format is PDF, but user may change; color mode is set to B/W and user may not change).

Step 2: User sets parameters for the job using one of the native imaging device modes or a standard RCD application. At the end of this step the user makes an input to initiate the job. When the input is made, an optional notification may be sent to the standard RCD application, which can then change job parameters if desired. An e-mail application is one example of an application that may request notification when the user input is made. A user may use native Image Send screens or other input to select scan options and choose e-mail recipients. A user may then select a custom application button and choose the scan-to-e-mail option from the menu. The e-mail application may then display custom screens for the user to set permissions for the file. Once a user places the original document(s) on the scanner and initiates the process, the e-mail application may capture the destination parameters set by the user and change the target destination to the e-mail application FTP server. The e-mail application may then receive the file, apply the appropriate permissions, and send to the e-mail recipients selected by the user. A remote computing device application may also want to retake control of the UI at this point, if, as in some embodiments, the application generates thumbnails of the scanned images and displays them to the user for verification.

Step 3: Once the job is initiated, the imaging device is responsible for scanning or RIPing the job and spooling it to the HDD. If the imaging device is configured to authorize jobs with an external authorization application, it may send a click report to the application and wait for instructions. The external authorization application may enable the job for sending/printing, cancel the job, or change job parameters (and then enable). As an example, a rules-based printing application may wish to change job parameters after it receives a click report. Some rules-based printing applications support rules-based printing and scanning that can limit what each user is allowed to do based on the time of day, the destination, or many other parameters. For example, only users in the marketing group may be able to scan high-quality color images. If a user from another group selects color and 600 dpi, a rules-based application may change the parameters to color and 200 dpi. At the end of this step the job should either be authorized or canceled.

Step 4: In some embodiments, this may be an optional step, where the standard RCD application in step 2 may have specified the destination as a HDD for temporary storage. This step may also be used, in some embodiments, by a Java application running on the imaging device. For example, a government office may have a custom encryption application running on the device that takes the scanned document, encrypts it, and then requests the imaging device to send it to the target destination selected by the user in step 2. In some embodiments, it may be beneficial to send a notification to the external authorization application after this step—because the imaging device does not know how long the file will be on the HDD or what the application is going to do with it—and after the send/print step.

Step 5: In the final step, the file is actually output. In typical embodiments, the file is either sent over the network or printed locally. At the end of this step, a notification that the job was successfully completed should be sent to the external authorization application and optionally, to the standard RCD application.

Device Control and Management API's

The API's may be used to allow a remote computing device application to control access to an imaging device for vend applications and to manage the device from a remote location.

Device Control and Vend API

In some embodiments of the present invention, a Device Control and Vend API allows applications to enable and disable access to the device and track click counts. The Device Control and Vend API may provide an RCD with the following controls:

Enable/disable device of function—this may allow an RCD to enable or disable access to the device as a whole or by function to enforce individual user privileges. In some exemplary embodiments, the functions listed in Table 3 may be selectively enabled or disabled by an application.

TABLE 3 Device Functions Enable/Disable Description Copy Copy function (Copy button) Image Send Scan and fax function, plus send from Doc Filing (Image Send button) Document Filing All access to Document Filing functions (Document Filing button) Print Network prints, pull print from front panel, and print from Document Filing (No button control)

Report clicks used—at the end of a successful job, the clicks used may be reported back to an RCD including:

TABLE 4 Job and Page Characteristics Fax PC- E-mail/ Broad- Scan Item Copy Print Send Fax FTP cast to HD JOB Characteristics Job Mode Yes Yes Yes Yes Yes Yes Yes Broadcast No No Yes Yes Yes Yes No Manage No. User Name Yes Yes Yes Yes Yes Yes Yes Address No No Yes Yes Yes # No Start Time Yes Yes Yes Yes Yes Yes Yes End Time Yes Yes Yes Yes Yes Yes Yes Total Page Yes Yes Yes Yes Yes Yes Yes Result Yes Yes Yes Yes Yes Yes Yes Error Cause No No Yes Yes Yes Yes No Doc Filing Yes Yes Yes Yes Yes Yes Yes Save Mode *1 *1 *1 *1 *1 *1 *1 File Name *1 Yes *1 Yes Yes *1 Yes File Size Yes Yes *1 *1 *1 *1 Yes Resolution Yes Yes Yes Yes Yes Yes Yes Special Yes Yes Yes No Yes Yes Yes Finishing Yes Yes No No No No No File Format No No No No Yes Yes No Compression No No No No Yes Yes No PAGE Characteristics Copy Yes Yes Yes Yes Yes # Yes Paper Size Yes Yes Yes Yes Yes Yes Yes Simplex/duplex Yes Yes Yes Yes Yes Yes Yes Paper Type Yes Yes Yes Yes No No Yes Page Yes Yes Yes Yes Yes Yes Yes *1 - Yes when Document Filing is used

Debit mode—in these embodiments, when an application enables the device it may specify if the current job requires authorization. If so, the job will be spooled to memory and click information (e.g., as defined in Table 4) will be sent to an RCD. An RCD will then notify the device if the job should be deleted or output/sent. At this point, the application also has the option of changing job parameters. If the application does not require authorization, the job will continue as normal and a click report will be sent at the end of the job.

Print job accounting—in these embodiments, an RCD may wish to monitor print jobs along with walk-up functions. For print job accounting, an IDev may monitor all incoming print jobs and send accounting data in the PJL header to an RCD for verification before printing the job. The RCD will evaluate the accounting data (or lack thereof) and inform the IDev to continue with or cancel the job.

Report on unidentified jobs—in these embodiments, an RCD may also wish to monitor print jobs that it cannot associate to a specific user, such as device reports and incoming fax jobs. The RCD can register to receive click counts for all unidentified jobs, so that it may bill them to a general account.

Device Management API

In some embodiments of the present invention, a Device Management API allows a network application to remotely setup and manage the imaging device. In exemplary embodiments, the Device Management API may provide an RCD with the following controls:

-   -   Device status—an RCD may request the current status of the         device. This is the same status information as reported on the         embedded web pages.     -   Device configuration—an RCD can retrieve a list of installed         options supported by the device.     -   Web Page settings—an RCD application can retrieve and set any of         the values that are configurable on the embedded web pages.     -   Key Operator Programs—an RCD application can retrieve and set         any of the values that are configurable in Key Operator         Programs, including software keys.     -   Custom Settings—an RCD application can retrieve and set any of         the values that are configurable in Custom Settings.     -   Job Status—an RCD application can retrieve the current job queue         and history information and reprioritize or delete jobs in the         queue.     -   Click counts—an RCD application can retrieve device total counts         and clicks for each function by account code.     -   Data Security settings—an RCD application may retrieve the         status information on the DSK (e.g. last erase) and initiate         data clear functions.     -   RED data—an RCD can retrieve all data typically sent in a RED         message.     -   Remote reboot—an RCD can initiate a reboot of the imaging         device.

The above groupings are provided only as an exemplary embodiment detailing which settings should be included. In some embodiments, actual API's should be grouped by functional areas since there may be overlap between Key Operator settings and web page settings.

Internal Accounting API

In some embodiments, an Internal Accounting API may allow a remote computing device application to configure internal accounting and report click counts. In some exemplary embodiments an Internal Accounting API may include:

-   -   Set Auditing Options—an RCD may set auditing options including         which modes auditing is enabled for, “account number security”,         and “cancel jobs of invalid accounts.”     -   Manage Account Codes—an RCD can add, edit, or delete account         codes     -   Account Limits—an RCD application can specify a maximum number         of clicks by function for individual account codes or for all         account codes     -   Account Reset—an RCD application can reset the click count for         an individual account or for all accounts     -   Retrieve Clicks—an RCD can retrieve the number of clicks by         function for each account code         Font and Form Management API

Some embodiments of the present invention may comprise a Font and Form Management API, which allows an RCD application to remotely download and manage fonts and forms in mass-storage. In some exemplary embodiments, a Font and Form Management API may provide a remote computing device with the following controls:

-   -   Mass storage control—an RCD application can retrieve mass         storage status information including storage capacity, space         available, and write-protect mode plus modify write-protect         status.     -   Resource list—an RCD application can retrieve a list of stored         fonts and forms including font or macro ID, font number,         font/form name, escape sequence, and file size.     -   Download resource—an RCD application can download PCL fonts, PCL         macros, and PS fonts and forms. Any special processing that is         performed when a resource is downloaded via the web pages will         also be performed when the resource is downloaded via Open         Systems.     -   Delete resource—an RCD application can delete any resource         stored in mass storage.     -   Upload resources—an RCD application can upload an individual or         all resources. On devices where effective memory management is         unavailable, a server application can use this function to         “defrag” mass storage.     -   Font/macro ID's—an RCD application can assign or modify the ID's         assigned to PCL fonts and macros.         Firmware Management API

In some embodiments of the present invention, a Firmware Management API may allow a remote computing device or network application to remotely download and manage the imaging device firmware. In some exemplary embodiments, a Firmware Management API may provide a remote computing device (e.g., a server) with the following controls:

-   -   Firmware versions—an RCD application can retrieve the current         firmware version numbers.     -   Service mode—an RCD application can place the MFP in service         mode to lockout other jobs that will interfere with firmware         upgrade. Upon receiving a service mode request, the IDev will         stop accepting incoming jobs, complete all jobs in the queue,         and then notify the server that it is in service mode.     -   Update firmware—an RCD can download an updated firmware version         to the device. If a reboot is necessary, the IDev will perform         it automatically when download is complete.     -   Download status—the IDev will send a status notification         (success/error) to an RCD after firmware download.     -   Revert to previous version—if firmware update is not successful,         the application can request the IDev to revert to the previous         firmware version.

Device Function API's

In some embodiments of the present invention, device function API's allow a remote computing device application to use existing imaging device functionality to provide new custom solutions.

Image Send API

In some embodiments, an Image Send API may provide the remote computing device application with the following controls:

-   -   Image Send Parameters—a remote computing device application can         get and set values for the following scan and fax parameters:         -   COLOR OR B/W         -   IMAGE MODE—TEXT, TEXT/PHOTO, PHOTO; EXPOSURE LEVEL         -   RESOLUTION         -   a FILE FORMAT—FILE TYPE, COMPRESSION, AND PAGES PER FILE         -   ORIGINAL—ORIGINAL SIZE, SIMPLEX/DUPLEX, ROTATE, AND JOB             BUILD         -   FILENAME         -   SUBJECT         -   MESSAGE         -   SENDER         -   SCHEDULE SEND TIME         -   PAGE DIVISION (BOOK SCANNING)         -   COVER PAGE         -   TRANSMISSION MESSAGE (CONFIDENTIAL, URGENT, ETC.)         -   THIN PAPER SCANNING         -   DESTINATION         -   DOCUMENT FILING     -   Initiate Scan—the remote computing device application can         initiate the scan function (same as user pressing start button).

In some embodiments, a remote computing device can change the default values on the imaging device or the values for the current job. For the current job, the remote computing device may also specify if scan parameters may be modified by the user or not. If one remote computing device application (e.g. Access Control) specifies that a parameter cannot be changed and then a second application (e.g. Document Management) tries to set the parameter, a notification may be sent to the second application and the setting will not be changed.

Print API

In some embodiments, print jobs may be submitted by remote computing device applications using standard printing channels. In some exemplary embodiments, a Print API may provide a remote computing device with the following additional control:

-   -   PJL sniffing—an RCD application can register with the IDev to be         contacted for instructions when a specific PJL command is found         in a print job. The RCD can then instruct the IDev to replace         the command, cancel the job, or continue printing. This         interface may be used in applications like accounting and         other-brand compatibility.         Copy API

In some embodiments of the present invention, a Copy API may provide a remote computing device with the following exemplary controls:

-   -   Copy Parameters—an RCD application can get and set values for         the following copy parameters:         -   COLOR OR B/W         -   EXPOSURE—TEXT, TEXT/PHOTO, PHOTO, SUPER PHOTO; EXPOSURE             LEVEL         -   PAPER SELECT (BY TRAY)         -   COPY RATIO         -   2-SIDED COPY—1TO1, 1TO2, 2TO2, 2T1; BINDING EDGE         -   OUTPUT—OUTPUT TRAY, SORT, STAPLE, GROUP, OFSET         -   ORIGINAL SIZE         -   SPECIAL FUNCTIONS—MARGIN SHIFT, ERASE, PAMPHLET, ETC.         -   DOCUMENT FILING     -   Initiate Copy—an RCD application can initiate the copy function         (same as user pressing start button).

In some embodiments, a remote computing device can change the default values on the imaging device or the values for the current job. For the current job, the remote computing device may also specify if copy parameters may be modified by the user or not.

Document Filing API

In some embodiments of the present invention, a Document Filing API may provide a remote computing device with the following exemplary controls:

-   -   Backup/restore—the remote computing device application can         import and export a batch file with all Document Filing data. In         some embodiments, this package will be in a proprietary format         since it contains documents that are password-protected and         should not be accessed individually—this is typically for         restore in case of failure or cloning to other devices.     -   File/folder list—the remote computing device application can         retrieve, modify, and create new files and folders to be stored         on the IDev (also covered in device management).     -   Download file—the remote computing device can download a new         file to the Document Filing systems and specify folder,         filename, username, and password.     -   User list—the remote computing device application can retrieve,         modify, and create new users to be stored on the IDev (also         covered in device management).     -   HDD Status—the remote computing device application can retrieve         the current HDD status including the % allocated to the main         folder, quick folder, and custom folders and the % remaining.     -   Doc Filing Parameters—the remote computing device application         can get and set values for storing a file to Doc Filing         including:         -   EXPOSURE         -   RESOLUTION         -   ORIGINAL-SIZE, SIMPLEX/DUPLEX         -   FILE INFORMATION—USERNAME, FILENAME, FOLDER, CONFIDENTIAL,             PASSWORD         -   SPECIAL MODES-ERASE, DUAL PAGE COPY, 2IN1, JOB BUILD, CARD             SHOT     -   Initiate Print—the remote computing device application can         select a stored file and initiate a print including the         following parameters:         -   PAPER SIZE/SOURCE         -   OUTPUT—SORT/GROUP, OUTPUT TRAY, STAPLE, PUNCH, OFFSET         -   SIMPLEX/DUPLEX (TABLET/BOOKLET)         -   TANDEM PRINT         -   NUMBER OF COPIES         -   DELETE OR STORE AFTER PRINTING     -   Initiate Send—the remote computing device application can select         a stored file and initiate a send including the following         parameters:         -   RESOLUTION         -   FILE FORMAT         -   DESTINATION         -   TIMER         -   SENDER         -   FILENAME         -   SUBJECT         -   MESSAGE

Security

Allowing external applications to control an imaging device opens up the imaging device to new security vulnerabilities. In embodiments of the present invention that provide some security measures, the following exemplary items are security concerns that may be addressed by the remote computing device interface.

Access to remote computing device interfaces may be limited to valid applications. Embodiments provide extensive access and control of the imaging device, which poses a significant security risk. The interface of these embodiments may be protected from access by attackers, while maintaining ease of setup and use for valid solutions.

Confidential data (user credentials and job data) may be protected during network transfer. User credentials and job data may be secured during network transfer to ensure that it cannot be stolen, an intruder cannot monitor device activity, and a man-in-the-middle attack cannot change messages. Imaging devices may support Secure Sockets Layer (SSL) and other connections to ensure data is safe while being communicated between the imaging device and remote computing device applications.

Administrators may have the ability to lock-down imaging device access. For users with strict security policies, administrators may have the ability to disable access by remote computing devices or limit access to specific applications. Administrators may have an option to register the limited applications that they wish to access the imaging device interfaces.

Remote computing device applications may ensure the imaging device is not being “spoofed.” The remote computing device may be able to authenticate an imaging device that it is contract with it to ensure an intruder cannot imitate the imaging device to collect network configuration and password information, monitor file/folder structures of a document management system, or spoof security settings and DSK status of the imaging device.

A remote computing device may ensure that the server is not being “spoofed.” The imaging device must be able to authenticate all remote computing devices that it is in contact with to ensure that an intruder is not spoofing the remote computing device's IP address. By pretending to be the remote computing device, an intruder could steal user credentials, redirect scanned documents, change device settings or firmware, or bring down the access control system (either to provide access to unauthorized users or initiate a denial of service attack for valid users).

Access control/vend applications may not be compromised when a remote computing device is unavailable. When the remote computing device is unavailable, it may not be acceptable to provide open access to the device. If the remote computing device is unavailable at startup or becomes unavailable at anytime (e.g. someone disconnects network cable), the imaging device may immediately be disabled and an error message displayed.

An administrator may be able to adjust a security level based on company and application requirements. Security requirements can have a large impact on the time it takes to develop a remote computing device application and the resources required to implement the solution. Users using some embodiments may range from a small business with one imaging device, no IT staff, and a simple scan or print application to a large government office using access control and audit trails to track all device activity. The security measures used to protect imaging device interfaces may be adjustable by the administrator to match the target environment.

The imaging device and remote computing device applications may be able to hand-off user credentials. Users may be prompted to login at multiple points throughout a job. For example, an access control application or accounting application may control total device access, the imaging device may have user authentication enabled for Image Send, and a document management application may require user login before showing a folder list. In many environments, all of these applications will use a common user database. In some embodiments, it is, therefore, desirable for the applications to pass user credentials to each other, so that each one does not have to repeat the authentication process.

Some embodiments of the present invention may be described with reference to FIG. 3. These embodiments comprise an imaging device only, which is configured to interact with a remote computing device, such as a server through a communications link. The imaging device 30 comprises a user interface 32, which comprises a user input device 34, such as a keypad, one or more buttons, knobs or switches or a touch-screen panel and a display 36, which may comprise user input device 34 in the form of a touch-screen panel.

Imaging device 30 will typically be capable of performing one or more imaging functions including, but not limited to, scanning, printing, copying, facsimile transmission (sending and receiving) and others.

These embodiments further comprise a communications link 38, which may be a wired connection (as shown in FIG. 3) comprising a network cable, a Universal Serial Bus (USB) cable, a serial cable, a parallel cable, a power line communication connection such as a HomePlug connection or other wired connections. Alternatively, the communications link 38 may comprise a wireless connection, such as an IEEE 802.11(b) compliant connection, a Bluetooth connection, an Infrared Data Association (IrDA) connection or some other wireless connection.

The operation of some imaging device embodiments may be explained with reference to FIG. 4. In these embodiments, menu data is received 40 from a remote computing device (not shown in FIG. 3), which is connected to the imaging device 30 via the communication link 38 through a wired or wireless connection. This menu data is then displayed 42 on the imaging device user interface display 36. This display of remote menu data is intended to prompt a user to make an input on the user interface input device 34.

Imaging devices of these embodiments are further configured to accept input from a user in response to a display of remote menu data and communicate 44 that user input to a remote computing device. In some embodiments, this user input data will be processed by a remote computing device. This may comprise running an application on the remote computing device. This processing may also comprise accessing and communicating data that is stored on the remote computing device.

The imaging devices of these embodiments are further configured to receive 46 data resulting from processing the user input data. This may comprise data generated by an application running on the remote computing device in response to the user input. The imaging device may also receive data that was stored on a remote computing device, such as a file server, in response to processing the user input.

Once the imaging device 30 has received 46 the processed data, the imaging device 30 may perform 48 a native function in response to the data or using the data. For example, and not be way of limitation, the imaging device 30 may print a document that was stored on the remote computing device and modified on the remote computing device according to the user input. As another non-limiting example, the imaging device 30 may active or enable functions (i.e., scanning, copying, printing, fax transmission) on the imaging device in response to the receipt 46 of processed data.

Some, more specific, imaging device embodiments may be explained with reference to FIG. 5. In these embodiments, the imaging device 30 is configured to receive 50 menu data formatted in a markup language from a remote computing device. The communication link by which the menu data is communicated may be established and maintained using a Hypertext Transfer Protocol (HTTP). The markup language may comprise terms from Hypertext Markup Language (HTML), Extensible Markup Language (XML), Wireless Markup Language (WML), Extensible Hypertext Markup Language (XHTML) and/or other languages.

Once the menu data is received 50, it may be displayed 52 on the imaging device user interface display 36. As in previously described embodiments, the menu data is typically intended to prompt user input on imaging device user interface 32. Display 52 of the remotely-stored menu data may be accomplished with a browser application that is native to the imaging device 30.

In these embodiments, the imaging device 30 is further configured to route 54 user input received though its user interface 32 to a remote computing device. The remote computing device that receives the user input may then run an application or otherwise process the user input and return the results of the processing to the imaging device 30. Accordingly, the imaging device 30 is further configured to receive 56 processed data from a remote computing device. In some embodiments, the imaging device 30 may perform one or more functions in response to the receipt 56 of processed data.

Some embodiments of the present invention may be explained with reference to FIG. 6. These embodiments comprise a remote computing device (RCD) 60, which has a communications link 64. Communications link 64 may be a wired connection (as shown in FIG. 6) comprising a network cable, a Universal Serial Bus (USB) cable, a serial cable, a parallel cable, a powerline communication connection such as a HomePlug connection or other wired connections. Alternatively, the communications link 64 may comprise a wireless connection, such as an IEEE 802.11(b) compliant connection, a Bluetooth connection, an Infrared connection, such as those defined in the Infrared Data Association (IRDA) standard or some other wireless connection. In some embodiments, RCD 60 may further comprise a data storage device 62, which is typically a hard drive, but may also be an optical drive device, such as an array of compact disk drives, flash memory or some other storage device.

Embodiments of RCD 60 may be further described with reference to FIG. 7. In these embodiments, RCD 60 comprises a processor 72 for processing data and running programs such as operating systems and applications. RCD 60 may further comprise memory 74, which may be in the form of Random Access Memory (RAM) and Read Only Memory (ROM). Generally, any applications processed by processor 72 will be loaded into memory 74. RCD 60 may further comprise a network interface 78, which allows RCD 60 to communicate with other devices, such as an imaging device 30. In some embodiments, RCD 60 may also comprise a user interface 80, but this is not required in many embodiments. Storage 62 may be used to store applications and data that may be accessed by an imaging device 30 of embodiments of the present invention. Processor 72, memory 74, storage 62, network interface 78 and, optionally, user interface 80 are typically linked by a system bus 76 to enable data transfer between each component. Communications link 64 may couple the RCD 60 to other devices via network interface 78.

In some embodiments, described with reference to FIG. 8, an RCD 60 may comprise menu data stored on storage device 62 or in memory 74. This menu data may be configured for display on an imaging device user interface 32. Menu data may be stored in many formats and configurations. In some embodiments menu data may take the form of terms expressed with a markup language. The markup language may comprise terms from Hypertext Markup Language (HTML), Extensible Markup Language (XML), Wireless Markup Language (WML), Extensible Hypertext Markup Language (XHTML) and/or other languages. In these embodiments, menu data may be sent 82 through a communications link 64 to an imaging device 30. Accordingly, menu data configured for display on an imaging device is stored on RCD 60.

An RCD 60, of some embodiments, will be further configured to receive 84 user input obtained through the user interface 32 of an imaging device 30 and transferred to the RCD 60 over communications links 38 & 64. Once this input data is received at an RCD 60, the input data may be processed 86. This processing 86 may comprise conversion of the data to a new format, execution of commands contained within the data or some other process. Once the input data has been processed 86, the processed output may be sent 88 back to the imaging device 30 where the processed output may be used in an imaging device process or function.

In some embodiments, as described with reference to FIG. 9, an RCD 60 may send 90 menu data configured for an imaging device display 36 using a markup language. The markup language menu data is then received at the imaging device 30 and displayed to a user. Typically, this will prompt the user to enter an input on the imaging device user interface 32. This user input will then be sent by the imaging device 30 to the RCD 60. The RCD 60 will then receive 92 the input data prompted by the display of the menu data on the imaging device 30. Once received, the input data may be processed 94 on the RCD 60. Processing may comprise the selection, recordation and/or modification of a form, document or other data stored on RCD 60, the authorization of a user identified by the user input, the translation of a document input by the user, generation of a map or other directions related to user input or some other process or function.

Some embodiments of the present invention may be described with reference to FIGS. 10 & 11. These embodiments comprise at least one RCD 60 and a plurality of imaging devices 30 a-30 d. In these embodiments, at least one of the imaging devices 30 a-30 d comprises a user interface 32 with a display 36 and user input panel 34 that is integral with the display (i.e., touch-screen) or a separate input unit. RCD 60 is connected to imaging devices 30 a-30 d by a communications link and network 100 to enable data transmission between RCD 60 and imaging devices 30 a-30 d.

In these embodiments, menu data is stored on RCD 60 and sent 110 to at least one of the imaging devices 30 a-30 d where the menu data is displayed on a user interface. Any of Imaging devices 30 a-30 d that receive the menu data are configured to accept 112 and transmit 114 user input to an RCD 60. Once the user input data is received at the RCD, the data may be processed 116 as discussed in previously described embodiments. The result of processing 116 may then be sent 118 back to any combination of the imaging devices 30 a-30 d.

In these embodiments, a single RCD 60 may be used to provide processing power, resources and functionality to a plurality of imaging devices 30 a-30 d without reproducing these resources in each imaging device. In some embodiments, data generated by input on one imaging device 30 a may be directed to another imaging device 30 d for processed data output or final processing.

Some embodiments of the present invention may be described with reference to FIG. 12. In these embodiments, an imaging device (IDev) 120 comprises a user interface 124, which is capable of receiving user input and displaying data to a user. The user interface 124 will typically comprise a display, often in the form of a touch panel. The display may be used to display data to a user. This data may comprise menu data to prompt for a user selection or data entry, such as a user ID and password, form selection or some other input. The imaging device 120 has a communication link 122, which may comprise a typical computer network connection, a serial cable or some other wired or wireless communication link as described in other embodiments. The communication link 122 may connect the imaging device 120 to a remote computing device (RCD) 126 a, 126 b, such as a server. The RCD 126 a, 126 b may be used to store documents, such as forms, and other data and make that data accessible from the imaging device 120. The RCD 126 a, 126 b may also execute applications that interact with or receive input from the imaging device 120 and its user interface 124. In some embodiments, a database 125 may be linked to the imaging device 120 and/or an RCD 126 a, 126 b. In some embodiments, an RCD 126 b or database 125 may be connected to an IDev 120 over a wide area network such as the internet 128.

Access Credential Management Embodiments

Some embodiments of the present invention comprise methods and systems that provide for reduction or elimination of repeated submission of user credential data in a system with multiple, distinct, restricted services, wherein a unique credential is required for each sub-system. In a typical imaging device (IDev) system, IDevs may be placed under accounting control, meaning that they are connected to an application running on a server that is tasked with recording the IDev's activity. In addition to recording activity, such as the number of copies made by each user, the accounting server application may also enable and disable certain or all functions of the IDev depending on a user's credentials. An accounting application or an access-control application may also control access to applications running on remote servers, depending on the credentials submitted by a user logging onto the device. In this manner, applications and functions may be restricted to specific users and fees may be charged to specific accounts for the use of specific applications and functions. An accounting application (AcctApp) comprises an access control application (ACA), typically to limit access to specific account holders.

In a typical system, when a user wishes to access a remote application, such as a document management system (DMS) or some other function or application, the user must first sign-on to the IDev accounting server application (AcctApp) or an access control application (ACA). This process may comprise submission of credentials and authentication of those credentials by the AcctApp. The user may then select an application such as a DMS, but will generally be asked to again submit DMS-specific user credentials to access this independent application. If the user then selects another function or application, the user may again be prompted to submit credentials specific to that function or application. For users with complex workloads, credential submission can be tedious, time consuming and difficult to manage.

Embodiments of the present invention comprise methods and systems that have the capability to eliminate multiple and sometimes redundant submission of user credential data by using a single sign-on server application (SSOSA) that manages credential data and dispenses the credentials to the appropriate services such as functions and/or applications. In some embodiments a SSOS may comprise a user credential data table capable of matching the credentials of authorized users with the credential requirements of all supported functions and applications. An exemplary user credential data table may comprise a column containing sign-on token data linked to other columns containing initial accounting server application credential data as well as columns containing sign-on credential data for all the supported functions and applications.

The SSOSA may operate as part of a network in conjunction with one or more IDevs, an accounting server application and one or more services including local and remote applications. Once user credentials have been submitted at an IDev they may be sent to an accounting server application or an access control application, which may communicate with the SSOSA. The SSOSA may access a data table or database containing user credential data to generate a single sign-on token that is related to the user's service credentials. This single sign-on token may then be transmitted by the IDev to one or more applications in lieu of varying credential data.

Some embodiments of the present invention may comprise an imaging device (IDev) in communication with one or more additional IDevs and/or one or more remote computing devices (RCDs). These devices may run applications that are remote to an IDev user, but in communication with a single sign-on server application (SSOSA).

Some exemplary embodiments of the present invention may be described with reference to FIG. 13A. These embodiments may comprise one or more networked, accounting-controlled imaging devices (IDevs) 130 that are in communication a single sign-on server application (SSOSA) 132. These one or more IDevs 130 may also be in communication with a remote service 131 such as a remote server application running on a remote computing device (RCD). These IDevs 130 may also have integrated functions 133A, 133B that are access-controlled and accessible only with approved credentials.

In these embodiments, an IDev 130 may send user sign-on credentials to the SSOSA 132, which may authenticate the credentials and issue a single-sign-on (SSO) token, which is related to the user's user service credentials for specific services, such as remote applications 131A & 131B and functions 133A & 133B. User service credentials are credentials that the user would typically use to gain access to the services and that the user would typically have to enter manually each time the user desires access to one or these services.

Once an SSO token is related to user service credentials and sent to an IDev 130, the IDev may use the token to automatically sign-on to the related services. When an IDev user selects a service 131A, the IDev sends the SSO token to the service 131A. The service 131A responds to the receipt of the token by forwarding the SSO token to the SSOSA 132, which recognizes the relationship to the user service credential and sends the user's credentials for that service to the service 131A. The service then authenticates the credentials and grants access to the user at the IDev 130. Other applications 131B and IDev functions 133A & 133B may be accessed in the same manner without input of service-specific credentials.

Some exemplary embodiments of the present invention may be described with reference to FIG. 13B. These embodiments may comprise one or more networked, accounting-controlled imaging devices (IDevs) 134 that are in communication with an accounting server application 135, which is also in communication with a single sign-on server application (SSOSA) 136. The IDev 134 may also be in communication with services 137 & 138, which may be remote applications or integrated functions 139A & 139B. These services, 137, 138, 139A & 139B may also be in communication with the SSOSA 136.

These embodiments illustrated in FIG. 13B operate similarly to those illustrate in FIG. 13A except that the accounting application 135 receives the user sign-on credential and authenticates the credential. The accounting application, upon successful authentication of the credential, requests an SSO token from the SSOSA 136, which is then relayed to the IDev 134. In this manner, the accounting application acts an intermediary between the IDev 134 and the SSOSA 136 and operates as an authentication application.

In some exemplary SSOSA embodiments, illustrated in FIG. 14, user credential data comprising user service credential data is stored in a table that relates a user to a single-sign-on (SSO) token, which is further related to user service credential data for specific services.

Methods followed by some embodiments of the present invention may be described with reference to FIG. 15. In these embodiments, a user may enter credentials at an IDev and send 150 the credentials to a SSOSA. The SSOSA may then authenticate 151 the credentials and, upon successful authentication 152, issue an SSO token to the user and send the SSO token 154 to the IDev for use by the user. The IDev will then store 156 the token and use the token for user authentication with services when needed.

An exemplary use of the SSO token may be described with reference to FIG. 16. In these exemplary embodiments, a user selects 161 an access-controlled service, which requires authentication. Instead of requiring user input of credentials, the IDev sends 162 the SSO token to the service. Upon receiving the SSO token, the service recognizes the token and sends 163 the token, or an equivalent token, to the SSOSA. The SSOSA will then receive the token and relate the token to the user service credential associated with the service that sent the token. The SSOSA will then send 164 the appropriate user service credential data to the service. The service will now be in possession of the user's service credential data and will authenticate 165 the user credentials to authorize access to the service. Upon successful authentication, the user, via the IDev, will be granted access 166 to the service.

Some embodiments of the present invention may be described with reference to FIG. 17. In these embodiments, a user enters log in credentials 170 at an IDev and sends the credentials to an accounting application or an access control application. The accounting or access control application then authenticates the user credentials 171 and, upon successful authentication, sends a request to a SSOSA to generate or assign a single-sign-on (SSO) token. The SSOSA will then generate or assign 172 the token and relate the token to the user's user service credential data. The SSOSA then sends 173 the SSO token to the accounting or access control application. The accounting or access control application then sends 174 the SSO token to the IDev, which stores 175 the SSO token for user authentication with services.

Use of the SSO token issued by the embodiments described in relation to FIG. 17 is similar to the exemplary use described in relation to FIG. 16. The SSO token is sent to a service in lieu of user credentials and the service works in cooperation with the SSOSA to obtain user service credential data for the service. The service may then authenticate the credential data supplied by the SSOSA and grant access based on that authentication.

Some embodiments of the present invention, illustrated in FIG. 18, comprise an imaging device (IDev) adapted to utilize one or more SSO tokens. In these embodiments, an IDev may accept 180 user sign-on credentials and send 181 those credentials to an SSOSA. When the credentials are successfully authenticated, the IDev will receive 184 an SSO token from the SSOSA and store 185 the SSO token for use in authenticating the user with access-controlled applications or functions. If the sign-on credentials do not authenticate successfully, the SSO token is not issued or sent to the IDev and further access to the system may be denied 183.

Some embodiments of the present invention, illustrated in FIG. 19, comprise an imaging device (IDev) adapted to communicate with an accounting application or another form of access-control application through which the IDev may acquire one or more SSO tokens from an SSOSA. In these embodiments, an IDev may accept 190 user sign-on credentials and send 181 those credentials to an accounting or access-control application. The accounting/access-control application may then perform authentication on the credentials to validate the user. When the credentials are successfully authenticated, the accounting/access-control application may send a request to an SSOSA for a SSO token for the IDev user. The SSOSA may then issue the token, as described above for other embodiments, and send the SSO token to the accounting/access-control application. The accounting/access-control application may then forward the SSO token to the IDev. The IDev-of these embodiments will then receive 194 the SSO token and store 195 the token for use with associated services.

Once the IDevs, described above in relation to FIGS. 18 and 19, have received and stored their SSO token, the tokens may be used to authenticate the user with associated services. This process may be described with reference to FIG. 20. In these embodiments, an IDev user selects 200 an access-controlled service. This service may be an integrated IDev function, such as a scan, print or copy function internal to the IDev or the service may be a remote application running on a remote computing device (RCD). In response to this service selection or a response from the service, the IDev may send 201 the SSO token to the selected service. The service may then respond by sending the SSO token to the SSOSA in exchange for user service credentials associated with that service. Upon receiving those credentials from the SSOSA, the service may authenticate 202 those credentials. If authentication is successful, the service will grant access to the IDev user and the IDev user will receive 204 this access and proceed with use of the service. If authentication is unsuccessful, access may be denied 203.

Some embodiments of the present invention comprise a single-sign-on server application (SSOSA) configured to communicate directly with an IDev. Some exemplary embodiments are illustrated in FIG. 21. In these embodiments, the SSOSA may receive 210 user sign-on credentials from an IDev. These credentials are then authenticated 211 to validate a user. If authentication is successful 212, the SSOSA will relate 214 a SSO token to the user's user service credentials and issue the token. The SSOSA may then send 215 the token to the IDev where the IDev may store the token and use it to authenticate the user with associated services.

Some embodiments of the present invention comprise a single-sign-on server application (SSOSA) configured to issue an SSO token to an IDev through an accounting or access-control application (AccApp). Some exemplary embodiments are illustrated in FIG. 22. In these embodiments, the SSOSA may receive 220 a request for an SSO token from an AccApp. In these embodiments, the AccApp has already authenticated user credentials and identified the user. The SSO token request from the AccApp will identify the user to the SSOSA. The SSOSA may then process this request by relating 221 an SSO token to the user's user service credentials and issuing the SSO token. The SSOSA may then send 222 the SSO token to the AccApp, which may forward the SSO token to the requesting IDev for use with associated services.

The SSOSA embodiments described in relation to FIGS. 21 and 22 comprise further functionality that may be described with reference to FIG. 23. In these embodiments, the SSOSA may receive 230 an SSO token from a service as a request for user service credentials. The SSOSA may respond to this request by matching 231 the SSO token received from the service to user service credential data stored in the SSOSA. Once these service credentials are retrieved in the SSOSA, they may be sent 232 to the service that made the request. Typically the requesting service will then authenticate the credentials and grant access to the associated user.

Some embodiments of the present invention comprise an accounting or access-control application configured to act as a gateway to an SSOSA. Some of these embodiments may be described in reference to FIG. 24. In these embodiments, an accounting/access control application (AccApp) may comprise an accounting application comprising a credential authentication process or an access-control application comprising an authentication process. In these embodiments, the AccApp may receive 240 user credentials, typically from an IDev. The AccApp may respond by authenticating 241 the credentials to validate the user. If the authentication process is successful 242, the AccApp may send 244 an SSO token request to an SSOSA. If the authentication process is not successful, no token request will be sent and further user access may be denied 243. Generally, the SSOSA will respond to the token request by relating an SSO token to the authenticated user's user service credential data and by sending the SSO token to the AccApp. The AccApp of these embodiments will then receive 245 the SSO token and send 246 the SS0 token to the IDev for use with associated services.

Some embodiments of the present invention comprise services that are configured to interact with IDevs and/or SSOSAs using SSO tokens and other communications. Some of these embodiments may be described with reference to FIG. 25. In these embodiments, an access-controlled service receives 250 an SSO token from an IDev. Typically this is done in lieu of user credential submission. The service may respond to the receipt of the SSO token by forwarding 251 the token to an SSOSA. In some embodiments, the token may be processed at the service to obtain user data or other information. The SSOSA will respond by retrieving user service credential data associated with the SSO token and sending the user service credential data to the requesting service. The services of these embodiments may then receive 252 the user service credential data and authenticate 253 the credentials to validate the IDev user. When authentication is successful, the service may grant 256 access to the user. If authentication is not successful, access may be denied 255.

The terms and expressions which have been employed in the forgoing specification are used therein as terms of description and not of limitation, and there is no intention in the use of such terms and expressions of excluding equivalence of the features shown and described or portions thereof, it being recognized that the scope of the invention is defined and limited only by the claims which follow. 

1. A method for providing single-credential access to multiple, distinct, restricted services wherein a unique credential is required for each service, said method comprising: displaying sign-on credential menu content on a display of said IDev; receiving user input comprising a sign-on credential at a user interface (UI) of said IDev; sending said sign-on credential to a single-sign-on server application (SSOSA) from said IDev; receiving a sign-on token, at said IDev, from said SSOSA, wherein said sign-on token is related to a user credential data table, which relates said sign-on token to a plurality of unique sign-on credentials for each of a plurality of IDev functions, services or applications and wherein said user credential data table and said credential are stored and maintained by said single-sign-on server application (SSOSA); sending said sign-on token to one of said plurality of IDev functions, services or applications for exchange by said one of said plurality of IDev functions, services or applications for a corresponding one of said unique sign-on credentials maintained at said SSOSA; and receiving access, at said IDev, to said one of said plurality of IDev functions, services or applications in response to said exchange.
 2. A method as described in claim 1 wherein said SSOSA is an application running on a remote computing device (RCD).
 3. A method as described in claim 1 wherein said service is an application running on a remote computing device (RCD).
 4. A method as described in claim 1 wherein said service is a local IDev function.
 5. A method as described in claim 1 wherein said sending user sign-on credentials is accomplished with an XML/SOAP message.
 6. A method for providing single-credential access to multiple, distinct, restricted services wherein a unique credential is required for each service, said method comprising: displaying sign-on credential menu content on a display of said IDev; receiving user input comprising a sign-on credential at a user interface (UI) of said IDev; sending said sign-on credentials to a single-sign-on server application (SSOSA) from said IDev; receiving a sign-on token, at said IDev, from said SSOSA when said user credential complies with authentication restrictions, wherein said sign-on token is related to a user credential data table, which relates said sign-on token to a plurality of unique sign-on credentials for each of a plurality of IDev functions, services or applications and wherein said user credential data table and said credential are stored and maintained by said single-sign-on server application (SSOSA); requesting access to a service by sending said sign-on token to said service, wherein receipt of said sign-on token causes said service to forward said sign-on token to said SSOSA and exchange said sign-on token for the unique sign-on credentials maintained at said SSOSA that correspond to said service; and receiving access to said service based on said unique sign-on credentials stored in said SSOSA.
 7. A method as described in claim 6 wherein said service is an IDev function.
 8. A method as described in claim 6 wherein said service is a remote application.
 9. A method as described in claim 6 wherein said requesting is accomplished with an XML/SOAP message.
 10. An apparatus for eliminating multiple submission of user credential data in a system with multiple, distinct, restricted services wherein a unique credential is required for each service, said apparatus comprising: an IDev display for displaying sign-on credential menu content on a display of said IDev; an IDev user interface (UI) for receiving user input comprising a sign-on credential at said IDev; a credential sender for sending said user sign-on credentials to a single-sign-on server application (SSOSA); a token receiver for receiving a sign-on token from said SSOSA when said user sign-on credential complies with authentication restrictions, wherein said token is related to a user credential data table, which relates said sign-on token to a plurality of unique sign-on credentials for each of a plurality of IDev functions, services or applications and wherein said user credential data table and said unique sign-on credentials are stored and maintained by said single-sign-on server application (SSOSA); a token sender for sending said sign-on token to one of said plurality of IDev functions, services or applications, wherein said sending causes said one of said plurality of IDev functions, services or applications to exchange said sign-on token for a corresponding one of said unique user service credentials maintained at said SSOSA, thereby gaining access to said one of said plurality of IDev functions, services or applications; a service connection receiver for receiving access to said one of said plurality of IDev functions, services or applications; and token storage for storing said sign-on token at said IDev.
 11. An apparatus as described in claim 10 wherein said SSOSA is an application running on a remote computing device (RCD).
 12. An apparatus as described in claim 10 wherein said service is an application running on a remote computing device (RCD).
 13. An apparatus as described in claim 10 wherein said service is a local IDev function. 